Forgive me if this is a duplicate query (or if it's something that should have been able to find on my own), but I have given up hope of finding an answer without posting this question. It seems like this should be an easy thing to do, but I'm still a relative novice with DOORS and not familiar with DXL. I have 3 Modules: Module A, Module B, and Module C. Module A is the top-level module and contains in-links to Module B. Module B has out-links to Module A and in-links to Module C. Module C has out-links to Module B. I have created an analysis column in Module A the shows the object IDs for the in-links to Module B. I have done the same in Module B for the in-links to Module C. My question is this: Is there a way for me to get the information from the analysis column in Module B to show in Module A? RoobyDooby - Mon Oct 06 14:56:45 EDT 2014 |
Re: Second Level Analysis If you have been creating Analysis columns then I assume that you have been using the DOORS Analysis Wizard tool to do this. It's just a simple case of configuring the Analysis Wizard tool In Module A to show linked information that is a depth of two link hops down from Module A - that is Module A to Module B is one link hop, then from Module B to Module C is the second link hop. When you get to Step 4 "Other Information" in the Analysis Wizard tool, you will see a check box "Recursive Analysis", select this and then either enter the value of 2 in the "Specify Depth" option or select the other option to "Display information only from selected modules" - if you selected the "Display..." option then when you select the "Next" button you will be asked to select which modules to include which in your case will be Module C. There is also the "Multiple Columns" option - when selected an analysis column is created for each individual link hop, if not selected then the analysis info is displayed in one column where the information for each link hop is indented - just need to try both choices to see what works for you.
Paul Miller
|
Re: Second Level Analysis One issue with this is that it you can get more than one path from a specific object oA1 from a specific object oC1; such as when oA1 is connected to oB1 and also oB2, and both of these are connected to oC1. Generally I think you would prefer that oA1 display oC1 just once in this case. Paul is correct but I prefer the following. In any case you definately would WANT to convert the outputs of the wizards to attr-DXL; complicated layouts chew up far too much CPU time. Write an Attr-DXL in B that shows in-link information from C. Note that this attr-dxl will need to open C, which will stay open. Write an Attr-DXL in A that follows links from B, reads that attr-value, removes duplicates, and sets them. This attr-dxl will need to open B; reading a B object attr-value will then open C. An alternative would be to be more like Paul, the Attr-DXL in A follows links from B, then follows links from C, and keeps track of every C object in a Skip, then display all the information about all the C objects. -Louie |
Re: Second Level Analysis PRM - Mon Oct 06 16:51:41 EDT 2014 If you have been creating Analysis columns then I assume that you have been using the DOORS Analysis Wizard tool to do this. It's just a simple case of configuring the Analysis Wizard tool In Module A to show linked information that is a depth of two link hops down from Module A - that is Module A to Module B is one link hop, then from Module B to Module C is the second link hop. When you get to Step 4 "Other Information" in the Analysis Wizard tool, you will see a check box "Recursive Analysis", select this and then either enter the value of 2 in the "Specify Depth" option or select the other option to "Display information only from selected modules" - if you selected the "Display..." option then when you select the "Next" button you will be asked to select which modules to include which in your case will be Module C. There is also the "Multiple Columns" option - when selected an analysis column is created for each individual link hop, if not selected then the analysis info is displayed in one column where the information for each link hop is indented - just need to try both choices to see what works for you.
Paul Miller
Thank you, Paul. That's exactly what I needed. I figured there was a simple solution, but it was just escaping me. |
Re: Second Level Analysis llandale - Tue Oct 07 12:49:11 EDT 2014 One issue with this is that it you can get more than one path from a specific object oA1 from a specific object oC1; such as when oA1 is connected to oB1 and also oB2, and both of these are connected to oC1. Generally I think you would prefer that oA1 display oC1 just once in this case. Paul is correct but I prefer the following. In any case you definately would WANT to convert the outputs of the wizards to attr-DXL; complicated layouts chew up far too much CPU time. Write an Attr-DXL in B that shows in-link information from C. Note that this attr-dxl will need to open C, which will stay open. Write an Attr-DXL in A that follows links from B, reads that attr-value, removes duplicates, and sets them. This attr-dxl will need to open B; reading a B object attr-value will then open C. An alternative would be to be more like Paul, the Attr-DXL in A follows links from B, then follows links from C, and keeps track of every C object in a Skip, then display all the information about all the C objects. -Louie Thank you for the reply, Louie. DXL is a bit beyond my current level of expertise, though admittedly I'm intimidated by it and as such haven't spent much time trying to learn it. But perhaps this use would be a good place to start. |
Re: Second Level Analysis RoobyDooby - Tue Oct 07 13:27:44 EDT 2014 Thank you for the reply, Louie. DXL is a bit beyond my current level of expertise, though admittedly I'm intimidated by it and as such haven't spent much time trying to learn it. But perhaps this use would be a good place to start. You can run some sample DXL via the DXL Browsing tool, which is on the DXL window. You can also open up that DXL. So you can get it to Notepad with Copy-Paste and then run it, and try to follow the code vis-a-vis what it appeared to do. That's a fair way to get started. |